Add "Spice as an MCP gateway" example - #1763
Conversation
✅ Pull with Spice PassedPassing checks:
|
|
🚀 deployed to https://5e7d61a2.spiceai-org-website.pages.dev |
There was a problem hiding this comment.
Pull request overview
This PR extends the MCP feature documentation by adding an end-to-end example that positions Spice as a single MCP endpoint aggregating built-in tools plus proxied third-party MCP servers (GitHub and Jira), and links to an external cookbook for a runnable setup.
Changes:
- Adds a new “Spice as an MCP gateway for GitHub and Jira” section with a full Spicepod configuration example.
- Documents expected combined tool catalog contents and a Claude Code connection command.
- Links to the
mcp-servercookbook for a complete runnable example.
Comments suppressed due to low confidence (2)
website/docs/features/large-language-models/mcp.md:182
- This sentence implies the header shown below is always required, but API key auth is optional. Consider clarifying that the header is only needed when
runtime.auth.api-keyis enabled.
Connect Claude Code to this gateway with a single command:
website/docs/features/large-language-models/mcp.md:185
- The docs use
X-API-Keyas the canonical HTTP API key header name. Using a different casing here is inconsistent and makes copy/paste harder.
claude mcp add --transport http spice http://localhost:8090/v1/mcp --header "X-API-KEY: <key>"
|
🚀 deployed to https://52dd94c8.spiceai-org-website.pages.dev |
|
This one is green and idle rather than blocked: all 7 checks pass, every review thread is resolved, and Requested @lukekim, who reviewed and merged the last several |
|
This PR has been validated with real github/JIRA connections. Ready to be merged |
|
🚀 deployed to https://e1a8b6c4.spiceai-org-website.pages.dev |
🗣 Description
Add
Spice as an MCP gatewaysection toMCPpage with a link tomcp_servercookbook.